Storage array data protection using virtual machine data protection

ABSTRACT

Systems and methods for replicating data from storage. Snapshots are taken of the volumes in physical storage. The snapshot volumes are exposed to a virtual replication system. Using the snapshots, differential or changed data can be identified. The identified data is then replicated by the virtual replication system to a remove virtual replication system.

FIELD OF THE INVENTION

Embodiments of the present invention generally relate to systems andmethods for performing data protection operations. More particularly, atleast some embodiments of the invention relate to systems, hardware,software, computer-readable media, and methods for performing dataprotection operations including replication operations.

BACKGROUND

Data protection operations generally relate to the concept of protectingdata. Data can be protected in a wide variety of ways. A typical methodfor protecting production data is to generate backups of the productiondata. In the event of a problem with the production data, the backupscan be used to resolve the problem.

However, there are many different types of data protection operations.Data replication, for example, generally relates to the concept ofreplicating data from a source to a target. The details of replication,however, are much more complicated. For example, the management paradigmfor virtual replication systems and physical replication systems aredistinct and different. A physical replication system is not able tosimply replicate the data to a virtual system.

Further, simply exposing the physical volumes to a virtual systemconfigured to replicate the physical volumes does not work at leastbecause the IOs (Input/Outputs) to the physical system do not passthrough this virtual system. As a result, simply exposing the physicalvolumes to the virtual system fails. The ability to replicate data toboth a physical system and a virtual system is further complicated bythe fact that physical devices (e.g., logical unit numbers or LUNs) arenot typically present or are not prevalent in cloud offerings.Consequently, the ability to leverage the benefits of virtual systems inphysical systems is not trivial.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to describe the manner in which at least some of the advantagesand features of the invention may be obtained, a more particulardescription of embodiments of the invention will be rendered byreference to specific embodiments thereof which are illustrated in theappended drawings. Understanding that these drawings depict only typicalembodiments of the invention and are not therefore to be considered tobe limiting of its scope, embodiments of the invention will be describedand explained with additional specificity and detail through the use ofthe accompanying drawings, in which:

FIG. 1 illustrates and example of a data protection system that includesa virtual replication system or component;

FIG. 2 further illustrates an example of a method for replicating datawith a virtual replication system; and

FIG. 3 illustrates another example of a method for replicating data witha virtual replication system.

DETAILED DESCRIPTION OF SOME EXAMPLE EMBODIMENTS

Embodiments of the present invention generally relate to data protectionoperations. At least some embodiments of the invention relate tosystems, hardware, software, computer-readable media, and methods forperforming data protection operations. Examples of data protectionoperations include, but are not limited to, replication operations,backup operations, restore operations, disaster recovery operations,deduplication operations, and other similar and/or related operations.Embodiments further relate to protecting data stored in storage arraysusing virtual machines or virtual systems. Embodiments may be performedor implemented in local area networks (LAN), wide area networks (WAN),cellular networks, and/or cloud networks (e.g., datacenters) orcombinations thereof.

In general, embodiments of the invention relate to systems and methodsfor converting or handling physical data, such that the data iscompatible with a virtual system (e.g., a virtual business continuityand disaster recovery (BCDR) system). Embodiments of the invention areconfigured to replicate data from a physical system to a virtual system.Once replicated, the data can be consumed in other manners. Thereplicated data can be used to generate backups, configured for failoverpurposes, or the like or combination thereof.

Embodiments of the invention may replicate data from production dataitself and/or images, snapshots, or other copies of production data.Dell EMC RecoverPoint Data Protection Software and/or related appliancesare examples systems in which embodiments of the invention may beimplemented. Embodiments may be implemented, for example, on EMC VNX andXtremIO platforms or other storage platforms.

In one example, embodiments of the invention may include takingsnapshots of data such as production data. Using the snapshots, changeddata in the production data can be identified. For example, comparing acurrent snapshot with a previous snapshot allows changed areas or blocksto be identified. Replication can be performed by sending only thechanged areas or the changed blocks from the source to the target orreplica site.

More specifically, a snapshot represents or is a copy of production dataat the time the snapshot was taken. Replication can be performed usingsnapshots because the data in the snapshots is essentially fixed anddoes not change. This is more difficult with production data, which ischanging over time. Plus, as previously discussed, the IOs to theproduction data may not pass through the virtual replication systembecause the production applications are attached to the physicalstorage.

Embodiments of the invention allow the production data to be protectedusing virtual machines or virtual replication systems and facilitatesuse of the replicated data in an environment such as a cloud-basedstorage environment.

Identifying changes to source or production data in snap basedreplication can be performed in different manners. In one example, thesnapshots may use or be associated with change block tracking or otherdifferential mechanisms that allow the areas or blocks that haveactually changed to be transferred or replicated efficiently. Morespecifically, changed data or blocks can be tracked from a particularpoint in time such as the last time a backup of snapshot was performed.Changes to data can be determined based on a differential between acurrent snapshot and a previous snapshot. A bitmap may be used toidentify changed blocks.

In one example, a series of snapshots can be maintained. For example, afirst snapshot S1 is taken. Subsequently, a snapshot S2 is taken. Thechanged areas or changed data can be identified by differencing thesnapshots (S2−S1). These identified changes to data can be replicated.Once the replication of these differences is completed, S1 can bediscarded if desired. When a new snapshot S3 is taken, the differencesor changed data can be identified by differencing S3 and S2 (S3−S2).This allows the snapshot S2 to be discarded when appropriate. Thus,embodiments of the invention are able to identify the data that haschanged with respect to a snapshot such as a current snapshot. Thechanged data can be replicated.

Embodiments of the invention, after identifying the changed data,replicate the data to a replica site, which may also be associated witha virtual replication system.

FIG. 1 illustrates an example of a virtual replication system configuredto replicate data from a production site to a replica site. FIG. 1illustrates an example of a production site 100 that includes productionapplications 102 and production storage 104. The storage 104 may includestorage devices including storage arrays or other storage types ordevices and configurations. The production applications 102 may accessand use (e.g., read, write, copy, modify etc.) data 108, which may bechanging over time based on the operation of the applications 102.

The data 108 is stored on volumes 106. FIG. 1 illustrates that IOs tothe storage 104 and to the volumes 106 occur between the productionapplications 102 and the storage 104. As previously indicated, simplyexposing the volumes 106 to a virtual replication system will likelyfail, from the perspective of replication, because the IOs are notrecognized or seen by or exposed to the virtual replication system.

To perform data protection applications for the production site 100, avirtual replication system 120 is provided. The virtual replicationsystem 120 may include or be associated with a virtual machine 122 andother infrastructure such as hypervisor (ESX) and control center(Vcenter). In this example, the virtual replication system 120 isconfigured to perform snapshot based replication. When a snapshot of thevolumes 106 is triggered, snapshots 112 of the volumes 106 or of thedata 108 are performed and stored as the snapshots 112 on snapshotvolumes 110. In one example, there is a snapshot volume for each of thevolumes 106 or for each of the volumes 106 subject to replication.

In one example, a consistency group of volumes 1-n are subject to areplication operation. In this example, snapshot volumes (SV1-SVn) areprepared to correspond to the volumes (V1-Vn). The snapshots of volumeV1-Vn are stored, respectively, on snapshot volume SV1-SVn.

In FIG. 1, the snapshot volumes 110 (and thus the snapshots 112) areexposed to the virtual machine 122 (or to or through a hypervisor)using, by way of example only, raw disk mapping. Raw disk mappingexposes the snapshot volumes 110 as a virtual volume (e.g., VMDK) to thevirtual machine 122.

To further establish replication, a virtual replication system 130 mayalso be established and associated with a replica site 126. The replicasite 126 may be a remote system or based in the cloud or a datacenter,by way of example. The replica site 126 is associated with a targetstorage 134 that includes volumes 136. The volumes 136 may be similar tothe volumes 106. In one example, the volumes 136 have the sameconfiguration as the volumes 106. This facilitates the replication ofthe data 108 as the replicated data can be written to locations on thevolumes 136 that correspond to the source locations on the volumes 106.Alternatively, the data 138 can also be stored in different manners. Thedata 138 can also be backed up (e.g., by taking snapshots of thereplicated data 138). The data 138 can reflect the current ornear-current status of the data 108. There may a difference between thedata 108 and the data 138 due to the replication process. The snapshotsof the data 138 or of the volumes 136 thus correspond to backups of theproduction data.

In one example, the data 138 can be used in a physical to virtualtransformation. If the production site 100 includes a machine that isdirectly mapped to storage devices such as LUNs, the replicated data 138can be transformed, at the replication site 126 to be a virtual machinemapped to virtual devices.

The virtual replication systems 120 and 130 may each include virtualmachines and related infrastructure such as hypervisors and controlcenters. The virtual replication systems 120 and 130 may be replicationappliances (physical and or virtual) and may be configured tocommunicate over a network. Once the replication system is set up asillustrated in FIG. 1, the data sweep or replication of the volumes 106can be performed.

During replication, the virtual replication system 120 may trigger aprotection cycle or a snap based replication cycle. This causes thesnapshots 112 to be refreshed with new or current snapshots whilekeeping change tracking bits or snapshot differential data or otherinformation that identifies changes to the data or that allows thechanges to be obtained. The virtual replication system 120 can then readthe tracking bits or the calculated differential areas. These areas maybe marked as changed. The changes areas or blocks are then synchronizedor replicated to the virtual replication system 130.

The replica site 126 can handle the received data in different ways. Thereceived data can be journaled, which may allow for continuous backups.The received data can be placed in snap arrays that do not supportjournaling. In this case, a snap base cycle may be performed at thereplica site 126 in order to store multiple points in time. In addition,the received data can be sent to the cloud or other locations.

The virtual replication system 130 may communicate with or be associatedwith a virtual infrastructure (e.g., VCenter and ESXs) to manage virtualmachines and prepare the replicated data for consumption. The replicateddata may be used as backups or to generate backups, as a failoversystem, or the like.

FIG. 2 illustrates an example of a method for replicating data. FIG. 2allows for the replication of both physical and virtual systems using asingle virtual replication system. Embodiments of the invention furtherexpose physical storage to virtual use cases and bring the advantagesand ease of use of maintaining replication systems including virtualreplication systems to a physical storage.

In FIG. 2, a virtual machine is created 202 and configured to replicatea storage group such as a consistency group of volumes of physicalstorage. Creating the virtual machine may be part of implementing avirtual replication system, which may also include virtualinfrastructure and support. Snapshot volumes may also be created.

Next, the snapshot volumes are exposed 204 to the virtual machine. Inone example, the virtual replication system may create a virtual machinewith snapshot volumes SV1-SVn attached to the virtual machine using rawdevice mapping techniques. In particularly, the snapshot volumes may beexposed to a hypervisor such as ESX and the virtual machine is placed onthe hypervisors where the snapshot volumes are exposed or mounted.

When the target or replica site is a storage array, a similar virtualenvironment or system may be initiated or created 206 at the targetsite. Replication is then performed 208 once protection is establishedand the data identified by the snapshots can be transferred orreplicated. The virtual replication system at the replica site may writethe data to virtual disks or volumes that correspond to the volumesbeing replicated.

FIG. 3 illustrates an example of a method for sending the data beingreplicated or the changed data from the source to the target. In oneexample, a protection cycle is initiated 302. The protection cycle (orsnap based replication) cycle may refresh the snapshots of the volumesbeing replicated. The protection cycle may also keep change trackingbits or snapshot differential data. For example, a current snapshot canbe compared to an older snapshot to identify a snapshot differential andto identify the changed data or areas. In this manner, the changed areasor blocks are identified 304.

The changed areas or blocks are then replicated 306. The snapshotvolumes can be read by the virtual replication system to retrieve thechanged data and the changed data can be sent to the replica site. Inaddition to replicating the data, virtual replication allows for sendingdata to the cloud. Image access and failover continue to be available.

Embodiments of the invention, such as the examples disclosed herein, maybe beneficial in a variety of respects. For example, and as will beapparent from the present disclosure, one or more embodiments of theinvention may provide one or more advantageous and unexpected effects,in any combination, some examples of which are set forth below. Itshould be noted that such effects are neither intended, nor should beconstrued, to limit the scope of the claimed invention in any way. Itshould further be noted that nothing herein should be construed asconstituting an essential or indispensable element of any invention orembodiment. Rather, various aspects of the disclosed embodiments may becombined in a variety of ways so as to define yet further embodiments.Such further embodiments are considered as being within the scope ofthis disclosure. As well, none of the embodiments embraced within thescope of this disclosure should be construed as resolving, or beinglimited to the resolution of, any particular problem(s). Nor should anysuch embodiments be construed to implement, or be limited toimplementation of, any particular technical effect(s) or solution(s).Finally, it is not required that any embodiment implement any of theadvantageous and unexpected effects disclosed herein.

In particular, one advantageous aspect of at least some embodiments ofthe invention allow data associated with a physical replication systemto also be used with a virtual management paradigm. Data can be managedusing a virtual data protection paradigm, which may include sending datato the cloud. Embodiments of the invention allow data protected orreplicated by physical protection systems to be protected or replicatedby virtual protection operations. As discussed herein, a journal may beused as a cascading mechanism to connect between the two differentsystems.

The following is a discussion of aspects of example operatingenvironments for various embodiments of the invention. This discussionis not intended to limit the scope of the invention, or theapplicability of the embodiments, in any way.

In general, embodiments of the invention may be implemented inconnection with systems, software, and components, that individuallyand/or collectively implement, and/or cause the implementation of, dataprotection operations including replication operations, backupoperations, restore operations, or the like or combination thereof.Additional operations may include, but are not limited to, dataread/write/delete operations, data deduplication operations, data backupoperations, data restore operations, data cloning operations, dataarchiving operations, and disaster recovery operations. More generally,the scope of the invention embraces any operating environment in whichthe disclosed concepts may be useful.

At least some embodiments of the invention provide for theimplementation of the disclosed functionality in existing backupplatforms, examples of which include the Dell-EMC NetWorker and Avamarplatforms and associated backup software, and storage environments suchas the Dell-EMC DataDomain storage environment and RecoverPoint systems,whether implemented virtually or physically. In general however, thescope of the invention is not limited to any particular data backupplatform or data storage environment or other data protection system.

New and/or modified data collected and/or generated in connection withsome embodiments, may be stored in a data protection environment thatmay take the form of a public or private cloud storage environment, anon-premises storage environment, and hybrid storage environments thatinclude public and private elements. Any of these example storageenvironments, may be partly, or completely, virtualized. The storageenvironment may comprise, or consist of, a datacenter which is operableto service read, write, delete, backup, restore, and/or cloning,operations initiated by one or more clients or other elements of theoperating environment. Where a backup comprises groups of data withdifferent respective characteristics, that data may be allocated, andstored, to different respective targets in the storage environment,where the targets each correspond to a data group having one or moreparticular characteristics.

Example public cloud storage environments in connection with whichembodiments of the invention may be employed include, but are notlimited to, Microsoft Azure, Amazon AWS, and Google Cloud. Moregenerally however, the scope of the invention is not limited toemployment of any particular type or implementation of cloud storage.

In addition to the storage environment, the operating environment mayalso include one or more clients that are capable of collecting,modifying, and creating, data. As such, a particular client may employ,or otherwise be associated with, one or more instances of each of one ormore applications that perform such operations with respect to data.

Devices in the operating environment may take the form of software,physical machines, or virtual machines (VM), containerized applications,or any combination of these, though no particular device implementationor configuration is required for any embodiment. Similarly, dataprotection system components such as databases, storage servers, storagevolumes (LUNs), storage disks, replication services, backup servers,restore servers, backup clients, and restore clients, for example, maylikewise take the form of software, physical machines or virtualmachines (VM), though no particular component implementation is requiredfor any embodiment. Where VMs are employed, a hypervisor or othervirtual machine monitor (VMM) may be employed to create and control theVMs. The term VM embraces, but is not limited to, any virtualization,emulation, or other representation, of one or more computing systemelements, such as computing system hardware. A VM may be based on one ormore computer architectures, and provides the functionality of aphysical computer. A VM implementation may comprise, or at least involvethe use of, hardware and/or software. An image of a VM may take variousforms, such as a .VMDK file for example.

As used herein, the term ‘data’ is intended to be broad in scope. Thus,that term embraces, by way of example and not limitation, data segmentssuch as may be produced by data stream segmentation processes, datachunks, data blocks, atomic data, emails, objects of any type, files ofany type including media files, word processing files, spreadsheetfiles, and database files, as well as contacts, directories,sub-directories, volumes, and any group of one or more of the foregoing.

Example embodiments of the invention are applicable to any systemcapable of storing and handling various types of objects, in analog,digital, or other form. Although terms such as document, file, segment,block, or object may be used by way of example, the principles of thedisclosure are not limited to any particular form of representing andstoring data or other information. Rather, such principles are equallyapplicable to any object capable of representing information.

As used herein, the term ‘backup’ is intended to be broad in scope. Assuch, example backups in connection with which embodiments of theinvention may be employed include, but are not limited to, full backups,partial backups, clones, snapshots, and incremental or differentialbackups.

For any of the aforementioned elements comprise or consist of a virtualmachine (VM), that VM may constitute a virtualization of any combinationof the physical components disclosed herein. A physical computing deviceincludes a memory which may include one, some, or all, of random accessmemory (RAM), non-volatile random access memory (NVRAM), read-onlymemory (ROM), and persistent memory, one or more hardware processors,non-transitory storage media, UI device, and data storage. One or moreof the memory components of the physical computing device may take theform of solid state device (SSD) storage. As well, one or moreapplications may be provided that comprise instructions executable byone or more hardware processors to perform any of the operations, orportions thereof, disclosed herein.

Such executable instructions may take various forms including, forexample, instructions executable to perform any method or portionthereof disclosed herein, and/or executable by/at any of a storage site,whether on-premises at an enterprise, or a cloud storage site, client,datacenter, or backup server, to perform any of the functions disclosedherein. As well, such instructions may be executable to perform any ofthe other operations and methods, and any portions thereof, disclosedherein including, but not limited to data protection operations.

Following are some further example embodiments of the invention. Theseare presented only by way of example and are not intended to limit thescope of the invention in any way.

Embodiment 1

A method for replicating data from storage of a production site, themethod comprising performing a protection cycle to create and storesnapshots of volumes on snapshot volumes, wherein the volumes storeproduction data, identifying changed data in the production data fromthe snapshots by a virtual data protection system that includes avirtual machine, and replicating the changed data to storage of areplica site by the virtual data protection system.

Embodiment 2

The method of embodiment 1, further comprising performing the protectioncycle on a consistency group.

Embodiment 3

The method of embodiment 1 and/or 2, further comprising exposing thesnapshot volumes to the virtual machine such that the snapshot volumesare virtual disks.

Embodiment 4

The method of embodiment 1, 2 and/or 3 further comprising exposing thesnapshot volumes using raw device mapping.

Embodiment 5

The method of embodiment 1, 2, 3, and/or 4, further comprisingidentifying the changed data using a changed bit tracker or snapshotdifferentials.

Embodiment 6

The method of embodiment 1, 2, 3, 4 and/or 5 further comprisingreplicating the changed data to a second virtual data protection systemassociated with the replica site.

Embodiment 7

The method of embodiment 1, 2, 3, 4, 5 and/or 6, wherein the secondvirtual data protection system comprises a virtual machine associatedwith virtual disks.

Embodiment 8

The method of embodiment 1, 2, 3, 4, 5, 6, and/or 7, wherein the virtualdisks are configured as volumes that correspond to the volumes beingreplicated.

Embodiment 9

The method of embodiment 1, 2, 3, 4, 5, 6, 7, and/or 8, wherein thevirtual data protection system comprises a replication appliance orwherein the protection system is initiated by the virtual dataprotection system.

Embodiment 10

The method of embodiment 1, 2, 3, 4, 5, 6, 7, 8, and/or 9, furthercomprising refreshing the snapshots of the volumes with new snapshots.

Embodiment 11

The method of embodiment of 1, 2, 3, 4, 5, 6, 7, 8, 9, and/or 10,further comprising repeatedly performing the protection cycle.

Embodiment 12

The method of embodiment 1, 2, 3, 4, 5, 6, 7,8, 9, 10 and/or 11, furthercomprising taking snapshots of the replicated data at the replica site.

Embodiment 13

The method of embodiment 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, and/or 12.

Embodiment 14

The method of embodiment 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, and/or13 further comprising journaling the replicated data at the replica siteor placing the replicated data in a snapshot.

Embodiment 15

A method for replicating data from a production site to a replica site,the method comprising providing a virtual replication system thatincludes a virtual machine configured to replicate data, mountingsnapshot volumes at the production site to the virtual machine such thatthe snapshot volumes are virtual disks to the virtual machine,performing or initiating a snap based replication cycle, by the virtualreplication system, to generate snapshots of production data stored onvolumes, wherein the snapshots are stored on the snapshot volumes,identifying, by the virtual replication system, changed data in theproduction data from the snapshots, and sending, by the virtualreplication system, the changed data to the replica site.

Embodiment 16

The method of embodiment 15, further comprising performing the snapbased replication cycle on a consistency group that includes the volumessuch that the snapshots of the volumes are taken at the same time.

Embodiment 17

The method of embodiment 15 and/or 16, further comprising exposing thesnapshot volumes using raw device mapping when mounting the snapshotvolumes to the virtual machine.

Embodiment 18

The method of embodiment 15, 16, and/or 17 further comprisingidentifying the changed data using a changed bit tracker or snapshotdifferentials, wherein sending the changed data includes replicating thechanged data to a second virtual data protection system associated withthe replica site, wherein the replica site includes a second virtualdata protection system comprising a virtual machine associated withvirtual disks.

Embodiment 19

The method of embodiment 15, 16, 17, and/or 18, wherein the virtualdisks are configured as volumes that correspond to the volumes beingreplicated.

Embodiment 20

The method of claim 15, 16, 17, 18, and/or 19, further comprisingrepeatedly performing the snap based replication cycle to refresh thesnapshots, wherein identifying the changed data includes performing asnapshot differential.

The embodiments disclosed herein may include the use of a specialpurpose or general-purpose computer including various computer hardwareor software modules, as discussed in greater detail below. A computermay include a processor and computer storage media carrying instructionsthat, when executed by the processor and/or caused to be executed by theprocessor, perform any one or more of the methods disclosed herein, orany part(s) of any method disclosed.

As indicated above, embodiments within the scope of the presentinvention also include computer storage media, which are physical mediafor carrying or having computer-executable instructions or datastructures stored thereon. Such computer storage media may be anyavailable physical media that may be accessed by a general purpose orspecial purpose computer.

By way of example, and not limitation, such computer storage media maycomprise hardware storage such as solid state disk/device (SSD), RAM,ROM, EEPROM, CD-ROM, flash memory, phase-change memory (“PCM”), or otheroptical disk storage, magnetic disk storage or other magnetic storagedevices, or any other hardware storage devices which may be used tostore program code in the form of computer-executable instructions ordata structures, which may be accessed and executed by a general-purposeor special-purpose computer system to implement the disclosedfunctionality of the invention. Combinations of the above should also beincluded within the scope of computer storage media. Such media are alsoexamples of non-transitory storage media, and non-transitory storagemedia also embraces cloud-based storage systems and structures, althoughthe scope of the invention is not limited to these examples ofnon-transitory storage media.

Computer-executable instructions comprise, for example, instructions anddata which cause a general purpose computer, special purpose computer,or special purpose processing device to perform a certain function orgroup of functions. Although the subject matter has been described inlanguage specific to structural features and/or methodological acts, itis to be understood that the subject matter defined in the appendedclaims is not necessarily limited to the specific features or actsdescribed above. Rather, the specific features and acts disclosed hereinare disclosed as example forms of implementing the claims.

As used herein, the term ‘module’ or ‘component’ may refer to softwareobjects or routines that execute on the computing system. The differentcomponents, modules, engines, and services described herein may beimplemented as objects or processes that execute on the computingsystem, for example, as separate threads. While the system and methodsdescribed herein may be implemented in software, implementations inhardware or a combination of software and hardware are also possible andcontemplated. In the present disclosure, a ‘computing entity’ may be anycomputing system as previously defined herein, or any module orcombination of modules running on a computing system.

In at least some instances, a hardware processor is provided that isoperable to carry out executable instructions for performing a method orprocess, such as the methods and processes disclosed herein. Thehardware processor may or may not comprise an element of other hardware,such as the computing devices and systems disclosed herein.

In terms of computing environments, embodiments of the invention may beperformed in client-server environments, whether network or localenvironments, or in any other suitable environment. Suitable operatingenvironments for at least some embodiments of the invention includecloud computing environments where one or more of a client, server, orother machine may reside and operate in a cloud environment. The orderof in which the methods or processes discussed herein may be performedsequentially, simultaneously, and/or in different orders.

The present invention may be embodied in other specific forms withoutdeparting from its spirit or essential characteristics. The describedembodiments are to be considered in all respects only as illustrativeand not restrictive. The scope of the invention is, therefore, indicatedby the appended claims rather than by the foregoing description. Allchanges which come within the meaning and range of equivalency of theclaims are to be embraced within their scope.

What is claimed is:
 1. A method for replicating data from storage of aproduction site, the method comprising: performing a protection cycle atthe production site to create and store snapshots of volumes on snapshotvolumes, wherein the volumes store production data; identifying changeddata in the production data from the snapshots by a virtual dataprotection system that includes a virtual machine; and replicating thechanged data to storage of a replica site by the virtual data protectionsystem.
 2. The method of claim 1, further comprising performing theprotection cycle on a consistency group.
 3. The method of claim 1,further comprising exposing the snapshot volumes to the virtual machinesuch that the snapshot volumes are virtual disks.
 4. The method of claim3, further comprising exposing the snapshot volumes using raw devicemapping.
 5. The method of claim 1, further comprising identifying thechanged data using a changed bit tracker or snapshot differentials. 6.The method of claim 1, further comprising replicating the changed datato a second virtual data protection system associated with the replicasite.
 7. The method of claim 6, wherein the second virtual dataprotection system comprises a virtual machine associated with virtualdisks.
 8. The method of claim 7, wherein the virtual disks areconfigured as volumes that correspond to the volumes being replicated.9. The method of claim 1, wherein the protection cycle is initiated bythe virtual data protection system.
 10. The method of claim 1, furthercomprising refreshing the snapshots of the volumes with new snapshots.11. The method of claim 1, further comprising repeatedly performing theprotection cycle.
 12. The method of claim 1, further comprising takingsnapshots of the replicated data at the replica site.
 13. The method ofclaim 1, further comprising journaling the replicated data at thereplica site or placing the replicated data in a snapshot.
 14. A methodfor replicating data from a production site to a replica site, themethod comprising: providing a virtual replication system that includesa virtual machine configured to replicate data; mounting snapshotvolumes at the production site to the virtual machine such that thesnapshot volumes are virtual disks to the virtual machine; initiating asnap based replication cycle, by the virtual replication system, togenerate snapshots of production data stored on volumes, wherein thesnapshots are stored on the snapshot volumes; identifying, by thevirtual replication system, changed data in the production data from thesnapshots; and sending, by the virtual replication system, the changeddata to the replica site.
 15. The method of claim 14, further comprisingperforming the snap based replication cycle on a consistency group thatincludes the volumes such that the snapshots of the volumes are taken atthe same time.
 16. The method of claim 14, further comprising exposingthe snapshot volumes using raw device mapping when mounting the snapshotvolumes to the virtual machine.
 17. The method of claim 14, furthercomprising identifying the changed data using a changed bit tracker orsnapshot differentials, wherein sending the changed data includesreplicating the changed data to a second virtual data protection systemassociated with the replica site, wherein the replica site includes asecond virtual data protection system comprising a virtual machineassociated with virtual disks.
 18. The method of claim 17, wherein thevirtual disks are configured as volumes that correspond to the volumesbeing replicated.
 19. The method of claim 1, further comprisingrepeatedly performing the snap based replication cycle to refresh thesnapshots, wherein identifying the changed data includes performing asnapshot differential.
 20. A non-transitory computer readable mediumcomprising computer executable instructions configured to implement themethod of claim 14.